Adding Recording Profiles
The Quick Start wizard process created an initial Recording profile for your tenant. You can then add additional recording profiles for targeted users.
➢ | Do the following: |
1. | In the Icon pane, click ![]() |
2. | Click New Profile. |
3. | Click Expand Settings to configure Pause and Resume functionality and ROD and SOD. |
4. | Configure profile according to the tables below. |
Field |
Description |
||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Profile Name |
Enter a name for the new recording profile. |
||||||||||||||||||||||||
Profile Description |
Enter a description of the new recording profile. |
||||||||||||||||||||||||
All |
Record all calls that the recording profile user participates in as calling party. This option is enabled by default or when a new recording profile is created. |
||||||||||||||||||||||||
Call Types (it's Mandatory to select at least one Call type) |
|||||||||||||||||||||||||
User Peer-to-Peer Calls When Call Types 'PSTN', 'Internal' or 'External' are enabled, and then the call is escalated to a Conference call (when additional parties are added to the call), the escalated Conference part of the call will be recorded as part of the original peer-to-peer call recording leg. |
|||||||||||||||||||||||||
Internal |
Refers to Peer-to-Peer calls between the targeted recording profile user and other users within the same domain. One of the following values:
|
||||||||||||||||||||||||
PSTN |
Refers to Peer-to-Peer calls between the Targeted recording profile user and parties outside of the organization's network on PSTN. One of the following values:
|
||||||||||||||||||||||||
External |
Refers to Peer-to-Peer calls between the Targeted recording profile user and parties with Federated domain or any public Microsoft Teams domain.
|
||||||||||||||||||||||||
User Calls with Meetings |
|||||||||||||||||||||||||
External Meetings |
Refers to Targeted user calls with meetings that are scheduled by External users and belong to an External organization. This option is supported by Microsoft Teams Integration and with “Full Time” Recording Type only. |
||||||||||||||||||||||||
Internal Meetings |
Refers to Targeted user calls with meetings that are scheduled by Internal users from the same domain as the Targeted user. This option records Teams calls with an Internal conference bridge in the Enterprise domain. An Internal Conference is a scheduled, ad-hoc meeting that occurs on a bridge belonging to the targeted user organization. When enabled, all user calls with internal meetings are recorded according to the below options. When disabled, none of the user calls with internal conferences are recorded. One of the following options:
|
||||||||||||||||||||||||
Expand Settings The below settings must be enabled by the Service Provider in the Service settings in the Tenant Management interface. |
|||||||||||||||||||||||||
Internal |
|
||||||||||||||||||||||||
PSTN |
|
||||||||||||||||||||||||
External |
|
||||||||||||||||||||||||
User Queue Calls |
|||||||||||||||||||||||||
Call Queues Instance ids |
Comma separated list of the call queue instance ids which should be recorded (see Retrieving Recording Queue Instances). Relevant when Teams Queue Calls (Transfer mode) is configured and "All" is not selected. When “All” is selected, all user calls will be recording including calls from any call queue. The maximum length of the field is 2048 characters. |
||||||||||||||||||||||||
Teams Queue Calls (transfer mode) |
Record Microsoft Teams calls that have been retrieved from a queue by a call agent. The recording is triggered as soon as the call is connected to an agent. Recording by IDs is only supported when routing method is set to 'Transfer'. |
||||||||||||||||||||||||
Save on Demand After Call Timer |
Elapsed time available to record call after the call has been terminated. |
||||||||||||||||||||||||
Storage Configuration |
|||||||||||||||||||||||||
Retention Period - Audio (Days) |
Call retention is the number of days to keep recordings in storage. Use the default with caution since eventually the storage location will be completely consumed. To meet business requirements, it's highly recommended to set the retention value to a positive number. Interaction Insights deletes calls that exceed the retention period once a day. A network administrator with appropriate security profile credentials has the option to add / modify retention policies.
Configure one of the following Retention period time frames:
|
||||||||||||||||||||||||
Storage |
Azure Blob Storage account location according to geographical region where the instance is installed. |
Advanced Settings
Field |
Description |
|||||||||
---|---|---|---|---|---|---|---|---|---|---|
Recording Notification |
Controls whether Microsoft Teams banner recording notifications are displayed:
This parameter is only displayed when enabled by the Service Provider in the Interaction Insights service. In addition, you must sign a waiver to enable this feature. |
|||||||||
Filter Calls User Receives Filter Calls User Makes |
To filter calls that the user receives or makes, choose the type of the filter. To record the user calls with specific numbers, choose Allow in the List Type. To record calls of the user except with specific numbers, choose Block: in the List Type. The Filter is applied on the calls with the comma-separated phone numbers defined in the Numbers field. For example: “17326524689, 17326524690” regular expression can be entered when the phone number ranges need to be filtered. For example, to filter calls with phone numbers that starts with area code 732 or 609, enter the following in the regular expression field:^(1{1}|\1{1})?(732|609)\d*$. When both the numbers and regular expressions are provided, the system first checks against the regular expression and if a match is not found, continues with the numbers. The maximum length of the numbers and the regular expression field is 2048 characters. Filtering is applicable to Skype for Business integrations and to Microsoft Teams (PSTN calls only). The + sign should not be added in Numbers and Regular Expression fields as its not recognized by Interaction Insights. |
|||||||||
Time Range |
Specify a time range for call recording, which includes the option to choose specific days of the week and time ranges based on the location of the server for the (product name) region. |
|||||||||
Custom Recording Hours |
Custom Recording Hours (default 24/7):
|
1. | Click Next to add groups. |
Users can only be mapped to one Recording Profile; however, can be assigned to multiple groups that are mapped to the same profile. In this case, the following message is displayed:
2. | Open the Azure portal of your tenant to verify which groups you wish to add. |
The following message is displayed if you have not yet synced groups with your M365 platform.
3. | Perform the Sync; a confirmation message is displayed. |
4. | Click Next to continue. |
5. | Configure the following Microsoft Teams Calling Policies: |
● | Disconnect Calls when Recorder Unavailable: Calls are disconnected when recording functionality is not available. |
● | Disable Compliance Recording Audio Notifications: Disable Microsoft Teams Audio Recording notifications that are played to calls participants from PSTN or other UC platforms. |
6. | Click the Download Configuration Script link to download the PowerShell script to your PC. |
You can also run the script at a later time using the right-click menu option MSFT Scripts (see Download and Run Microsoft Script).
7. | Run the script createProfileSuperProfile-dd-m-yyyy.ps1 as Administrator. |
8. | Enter the credentials of the Azure customer tenant account and authenticate using the Microsoft Authenticator when prompted. |
The script supports Multifactor authentication.
See example log file below (saved to Desktop on the PC where you run the script).
**********************
Windows PowerShell transcript start
Start time: 20240616123342
Username: LAPTOP-M8LNK8BQ\USER
RunAs User: LAPTOP-M8LNK8BQ\USER
Configuration Name:
Machine: LAPTOP-M8LNK8BQ (Microsoft Windows NT 10.0.19045.0)
Host Application: C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -ExecutionPolicy Bypass -File C:\Users\USER\Desktop\Powershell\editProfileSuperProfile-16-6-2024.ps1
Process ID: 19148
PSVersion: 5.1.19041.4522
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.19041.4522
BuildVersion: 10.0.19041.4522
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
**********************
Transcript started, output file is C:\Users\USER\desktop\MSTC_Policy06.16.12.33.txt
PS>TerminatingError(Invoke-RestMethod): "{"type":"https://tools.ietf.org/html/rfc7231#section-6.5.13","title":"Unsupported Media Type","status":415,"traceId":"00-1fa6a9561e39115c5b5258f162c5540d-a5c8015bfcd9c025-00"}"
6/16/2024 12:33:43 PM - Searching 'MicrosoftTeams' module...
6/16/2024 12:33:47 PM - 'MicrosoftTeams' module installed successfully.
6/16/2024 12:33:47 PM - Importing 'MicrosoftTeams' module...
INFO: Loaded Module 'Microsoft.Teams.ConfigAPI.Cmdlets'
6/16/2024 12:33:52 PM - 'MicrosoftTeams' module imported successfully.
6/16/2024 12:35:10 PM - Connected to Microsoft Teams successfully.
6/16/2024 12:35:10 PM - Getting recording policies...
6/16/2024 12:35:12 PM - Retrieved recording policies successfully.
6/16/2024 12:35:12 PM - fetching domains...
6/16/2024 12:35:15 PM - Domain M365x21689653.onmicrosoft.com fetched successfully.
6/16/2024 12:35:15 PM - SuperProfile06062024142032 already exists. Skipping policy creation.
6/16/2024 12:35:15 PM - Application Instance for SuperProfile06062024142032 already exist.
6/16/2024 12:35:16 PM - Starting Sync Process for SuperProfile06062024142032 ...
6/16/2024 12:35:18 PM - Sync Process for SuperProfile06062024142032 Finished.
6/16/2024 12:35:18 PM - SuperProfile06062024142032 already exist , skipping..
6/16/2024 12:35:18 PM - Configuring SuperProfile06062024142032 Recording Policy...
6/16/2024 12:35:24 PM - Configuring disconnectCalls True for SuperProfile06062024142032...
6/16/2024 12:35:26 PM - Configuring audioNotification False for SuperProfile06062024142032...
6/16/2024 12:35:27 PM - SuperProfile06062024142032 Recording Policy Has Been Configured.
6/16/2024 12:35:27 PM - Assigning groups to primary policy...
Adding 4d93b1c7-f944-4e82-a372-1ebe23979c6e to SuperProfile06062024142032.. please wait..
WARNING: Group 4d93b1c7-f944-4e82-a372-1ebe23979c6e already assigned to SuperProfile05302024155452 policy.
Force Assignment set to True, adding 4d93b1c7-f944-4e82-a372-1ebe23979c6e to SuperProfile06062024142032.. please wait..
Sending following status to API....
{
"TenantId": "5f4e3129-dd39-4ccd-bc4f-98423bee2c1b",
"Message": "Success",
"PolicyId": "SuperProfile06062024142032",
"StatusCode": 0
}
Results sent successfully and should be reflected in the UI
**********************
Windows PowerShell transcript end
End time: 20240616123533
**********************
9. | Once you have successfully run the script, verify that the Recording Profile status is 'Successful'. |